Alarm and diagnostics system and method for a distributed architecture heating, ventilation and air conditioning network

ABSTRACT

The disclosure includes an HVAC data processing and communication network and a method of manufacturing the same. In one embodiment the network includes a duct, a blower and a controller. The blower is configured to receive a control message from a data bus. The duct is configured to direct air flow from the blower. The controller is configured to publish the control message to the data bus. The controller thereby commands the blower to provide air to the duct at an initial volume rate and to increase the volume rate until the controller detects onset of a cutback mode of the blower.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Ser. No. 61/167,135, filed by Grohman, et al., on Apr. 6, 2009, entitled “Comprehensive HVAC Control System” and U.S. Provisional Application Ser. No. 61/852,676, filed by Grohman, et al., on Apr. 7, 2009, and is also a continuation-in-part application of application Ser. No. 12/258,659, filed by Grohman on Oct. 27, 2008 now abandoned, entitled “Apparatus and Method for Controlling an Environmental Conditioning Unit,” all which are commonly assigned with this application and incorporated herein by reference. This application is also related to the following U.S. patent applications, which are filed on even date herewith, commonly assigned with this application and incorporated herein by reference:

Serial No. Inventors Title 12/603,464 Grohman, “Alarm and Diagnostics System and Method et al. for a Distributed-Architecture Heating, Ventilation and Air Conditioning Network” 12/603,534 Wallaert, “Flush Wall Mount Control Unit and In- et al. Set Mounting Plate for a Heating, Ventilation and Air Conditioning System” 12/603,449 Thorson, “System and Method of Use for a User et al. Interface Dashboard of a Heating, Ventilation and Air Conditioning Network” 12/603,382 Grohman “Device Abstraction System and Method for a Distributed-Architecture Heating, Ventilation and Air Conditioning Network” 12/603,526 Grohman, “Communication Protocol System and et al. Method for a Distributed-Architecture Heating, Ventilation and Air Conditioning Network” 12/603,527 Hadzidedic “Memory Recovery Scheme and Data Structure in a Heating, Ventilation and Air Conditioning Network” 12/603,490 Grohman “System Recovery in a Heating, Ventilation and Air Conditioning Network” 12/603,473 Grohman, “System and Method for Zoning a et al. Distributed-Architecture Heating, Ventilation and Air Conditioning Network” 12/603,525 Grohman, “Method of Controlling Equipment in a et al. Heating, Ventilation and Air Conditioning Network” 12/603,512 Grohman, “Programming and Configuration in a et al. Heating, Ventilation and Air Conditioning Network” 12/603,431 Mirza, “General Control Techniques in a et al. Heating, Ventilation and Air Conditioning Network”

TECHNICAL FIELD

This application is directed, in general, to HVAC systems and, more specifically, to alarm and diagnostics system and method for a distributed-architecture heating, ventilation and air conditioning (HVAC) network.

BACKGROUND

Climate control systems, also referred to as HVAC systems (the two terms will be used herein interchangeably), are employed to regulate the temperature, humidity and air quality of premises, such as a residence, office, store, warehouse, vehicle, trailer, or commercial or entertainment venue. The most basic climate control systems either move air (typically by means of an air handler having a fan or blower), heat air (typically by means of a furnace) or cool air (typically by means of a compressor-driven refrigerant loop). A thermostat is typically included in a conventional climate control system to provide some level of automatic temperature and humidity control. In its simplest form, a thermostat turns the climate control system on or off as a function of a detected temperature. In a more complex form, the thermostat may take other factors, such as humidity or time, into consideration. Still, however, the operation of a thermostat remains turning the climate control system on or off in an attempt to maintain the temperature of the premises as close as possible to a desired set point temperature. Climate control systems as described above have been in wide use since the middle of the twentieth century and have, to date, generally provided adequate temperature management.

SUMMARY

One aspect the disclosure provides a method of manufacturing an HVAC data processing and communication network. In one embodiment the HVAC data processing and communication network includes a duct, a blower and a controller. The method includes configuring the duct to direct air flow from the blower. The blower is configured to receive a control message from a data bus. The controller is configured to publish the control message to the data bus. The controller thereby commands the blower to provide air to the duct at an initial volume rate and to increase the volume rate until the controller detects onset of a cutback mode of the blower.

In another aspect, the disclosure provides an HVAC data processing and communication network. In one embodiment the network includes a duct, a blower and a controller. The blower is configured to receive a control message from a data bus. The duct is configured to direct air flow from the blower. The controller is configured to publish the control message to the data bus. The controller thereby commands the blower to provide air to the duct at an initial volume rate and to increase the volume rate until the controller detects onset of a cutback mode of the blower.

Another aspect provides an HVAC data processing and communication network. In one embodiment the network includes a subnet controller, a first temperature sensor and a second temperature sensor. The subnet controller is configured to initiate a test procedure by sending a message including a service demand to a demand unit providing demand. The first temperature sensor is configured to measure a discharge temperature of discharge air provided by the demand unit in response to the service demand. The second temperature sensor is configured to measure an ambient temperature of a space conditioned by the network. The subnet controller is further configured to take mitigating action in the event that a temperature-time profile of the discharge air relative to the ambient temperature is inconsistent with the service demand.

In yet another aspect, the disclosure provides a method of manufacturing an HVAC data processing and communication network. In one embodiment the method includes configuring a subnet controller and a first and second temperature sensor. The subnet controller is configured to initiate a test procedure by sending a message including a service demand to a demand unit providing demand. The first temperature sensor is configured to measure a discharge temperature of discharge air provided by the demand unit in response to the service demand. The second temperature sensor is configured to measure an ambient temperature of a space conditioned by the network. The subnet controller is further configured to take mitigating action in the event that a temperature-time profile of the discharge air relative to the ambient temperature is inconsistent with the service demand.

BRIEF DESCRIPTION

Reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a high-level block diagram of an HVAC system according to various embodiments of the disclosure;

FIG. 2 is a high-level block diagram of one embodiment of an HVAC data processing and communication network;

FIG. 3 is a block diagram of a local controller of the disclosure;

FIG. 4 is a block diagram of a networked HVAC system device of the disclosure;

FIG. 5 is an embodiment of an HVAC data processing and communication network having two subnets;

FIG. 6 is a flow diagram of a method of the disclosure of testing air duct performance in an HVAC data processing and communication network;

FIG. 7 is a flow diagram of a series of steps in an event sequence that depicts operation of a networked HVAC system in response to blower alarm condition;

FIG. 8 illustrates an embodiment of an alarm display with flashing backlight;

FIGS. 9, 10A and 10B illustrate storage of alarm records;

FIGS. 11-24 and 26 illustrate various methods of the disclosure;

FIG. 25 illustrates an embodiment of sensing an outlet air temperature; and

FIGS. 27-30 illustrate aspects of alarm display on a user interface.

DETAILED DESCRIPTION

As stated above, conventional climate control systems have been in wide use since the middle of the twentieth century and have, to date, generally provided adequate temperature management. However, it has been realized that more sophisticated control and data acquisition and processing techniques may be developed and employed to improve the installation, operation and maintenance of climate control systems.

Described herein are various embodiments of an improved climate control, or HVAC, system in which at least multiple components thereof communicate with one another via a data bus. The communication allows identity, capability, status and operational data to be shared among the components. In some embodiments, the communication also allows commands to be given. As a result, the climate control system may be more flexible in terms of the number of different premises in which it may be installed, may be easier for an installer to install and configure, may be easier for a user to operate, may provide superior temperature and/or relative humidity (RH) control, may be more energy efficient, may be easier to diagnose, may require fewer, simpler repairs and may have a longer service life.

FIG. 1 is a high-level block diagram of a networked HVAC system, generally designated 100. The HVAC system 100 may be referred to herein simply as “system 100” for brevity. In one embodiment, the system 100 is configured to provide ventilation and therefore includes one or more air handlers 110. In an alternative embodiment, the ventilation includes one or more dampers 115 to control air flow through air ducts (not shown.) Such control may be used in various embodiments in which the system 100 is a zoned system. In an alternative embodiment, the system 100 is configured to provide heating and therefore includes one or more furnaces 120, typically associated with the one or more air handlers 110. In an alternative embodiment, the system 100 is configured to provide cooling and therefore includes one or more refrigerant evaporator coils 130, typically associated with the one or more air handlers 110. Such embodiment of the system 100 also includes one or more compressors 140 and associated condenser coils 142, which are typically associated with one or more so-called “outdoor units” 144. The one or more compressors 140 and associated condenser coils 142 are typically connected to an associated evaporator coil 130 by a refrigerant line 146. In an alternative embodiment, the system 100 is configured to provide ventilation, heating and cooling, in which case the one or more air handlers 110, furnaces 120 and evaporator coils 130 are associated with one or more “indoor units” 148, e.g., basement or attic units that may also include an air handler.

For convenience in the following discussion, a demand unit 155 is representative of the various units exemplified by the air handler 110, furnace 120, and compressor 140, and more generally includes an HVAC component that provides a service in response to control by the control unit 150. The service may be, e.g., heating, cooling, humidification, dehumidification, or air circulation. A demand unit 155 may provide more than one service, and if so, one service may be a primary service, and another service may be an ancillary service. For example, for a heating unit that also circulates air, the primary service may be heating, and the ancillary service may be air circulation (e.g. by a blower).

The demand unit 155 may have a maximum service capacity associated therewith. For example, the furnace 120 may have a maximum heat output (often expressed in terms of British Thermal Units (BTU) or Joules), or a blower may have a maximum airflow capacity (often expressed in terms of cubic feet per minute (CFM) or cubic meters per minute (CMM)). In some cases, the demand unit 155 may be configured to provide a primary or ancillary service in staged portions. For example, blower may have two or more motor speeds, with a CFM value associated with each motor speed.

One or more control units 150 control one or more of the one or more air handlers 110, the one or more furnaces 120 and/or the one or more compressors 140 to regulate the temperature of the premises, at least approximately. In various embodiments to be described, the one or more displays 170 provide additional functions such as operational, diagnostic and status message display and an attractive, visual interface that allows an installer, user or repairman to perform actions with respect to the system 100 more intuitively. Herein, the term “operator” will be used to refer collectively to any of the installer, the user and the repairman unless clarity is served by greater specificity.

One or more separate comfort sensors 160 may be associated with the one or more control units 150 and may also optionally be associated with one or more displays 170. The one or more comfort sensors 160 provide environmental data, e.g. temperature and/or humidity, to the one or more control units 150. An individual comfort sensor 160 may be physically located within a same enclosure or housing as the control unit 150, in a manner analogous with a conventional HVAC thermostat. In such cases, the commonly housed comfort sensor 160 may be addressed independently. However, the one or more comfort sensors 160 may be located separately and physically remote from the one or more control units 150. Also, an individual control unit 150 may be physically located within a same enclosure or housing as a display 170, again analogously with a conventional HVAC thermostat. In such embodiments, the commonly housed control unit 150 and display 170 may each be addressed independently. However, one or more of the displays 170 may be located within the system 100 separately from and/or physically remote to the control units 150. The one or more displays 170 may include a screen such as a liquid crystal or OLED display (not shown).

Although not shown in FIG. 1, the HVAC system 100 may include one or more heat pumps in lieu of or in addition to the one or more furnaces 120, and one or more compressors 140. One or more humidifiers or dehumidifiers may be employed to increase or decrease humidity. One or more dampers may be used to modulate air flow through ducts (not shown). Air cleaners and lights may be used to reduce air pollution. Air quality sensors may be used to determine overall air quality.

Finally, a data bus 180, which in the illustrated embodiment is a serial bus, couples the one or more air handlers 110, the one or more furnaces 120, the one or more evaporator condenser coils 142 and compressors 140, the one or more control units 150, the one or more remote comfort sensors 160 and the one or more displays 170 such that data may be communicated therebetween or thereamong. As will be understood, the data bus 180 may be advantageously employed to convey one or more alarm messages or one or more diagnostic messages. All or some parts of the data bus 180 may be implemented as a wired or wireless network.

The data bus 180 in some embodiments is implemented using the Bosch CAN (Controller Area Network) specification, revision 2, and may be synonymously referred to herein as a residential serial bus (RSBus) 180. The data bus 180 provides communication between or among the aforementioned elements of the network 200. It should be understood that the use of the term “residential” is nonlimiting; the network 200 may be employed in any premises whatsoever, fixed or mobile. Other embodiments of the data bus 180 are also contemplated, including e.g., a wireless bus, as mentioned previously, and 2-, 3- or 4-wire networks, including IEEE-1394 (Firewire™, i.LINK™, Lynx™), Ethernet, Universal Serial Bus (e.g., USB 1.x, 2.x, 3.x), or similar standards. In wireless embodiments, the data bus 180 may be implemented, e.g., using Bluetooth™, Zibgee or a similar wireless standard.

FIG. 2 is a high-level block diagram of one embodiment of an HVAC data processing and communication network 200 that may be employed in the HVAC system 100 of FIG. 1. One or more air handler controllers (AHCs) 210 may be associated with the one or more air handlers 110 of FIG. 1. One or more integrated furnace controllers (IFCs) 220 may be associated with the one or more furnaces 120. One or more damper controller modules 215, also referred to herein as a zone controller module 215, may be associated with the one or more dampers 115. One or more unitary controllers 225 may be associated with one or more evaporator coils 130 and one or more condenser coils 142 and compressors 140 of FIG. 1. The network 200 includes an active subnet controller (aSC) 230 a and an inactive subnet controller (iSC) 230 i. The aSC 230 a may act as a network controller of the system 100. The aSC 230 a is responsible for configuring and monitoring the system 100 and for implementation of heating, cooling, humidification, dehumidification, air quality, ventilation or any other functional algorithms therein. Two or more aSCs 230 a may also be employed to divide the network 200 into subnetworks, or subnets, simplifying network configuration, communication and control. Each subnet typically contains one indoor unit, one outdoor unit, a number of different accessories including humidifier, dehumidifier, electronic air cleaner, filter, etc., and a number of comfort sensors, subnet controllers and user interfaces. The iSC 230 i is a subnet controller that does not actively control the network 200. In some embodiments, the iSC 230 i listens to all messages broadcast over the data bus 180, and updates its internal memory to match that of the aSC 230 a. In this manner, the iSC 230 i may backup parameters stored by the aSC 230 a, and may be used as an active subnet controller if the aSC 230 a malfunctions. Typically there is only one aSC 230 a in a subnet, but there may be multiple iSCs therein, or no iSC at all. Herein, where the distinction between an active or a passive SC is not germane the subnet controller is referred to generally as an SC 230.

A user interface (UI) 240 provides a means by which an operator may communicate with the remainder of the network 200. In an alternative embodiment, a user interface/gateway (UI/G) 250 provides a means by which a remote operator or remote equipment may communicate with the remainder of the network 200. Such a remote operator or equipment is referred to generally as a remote entity. A comfort sensor interface 260, referred to herein interchangeably as a comfort sensor (CS) 260, may provide an interface between the data bus 180 and each of the one or more comfort sensors 160. The comfort sensor 260 may provide the aSC 230 a with current information about environmental conditions inside of the conditioned space, such as temperature, humidity and air quality.

For ease of description, any of the networked components of the HVAC system 100, e.g., the air handler 110, the damper 115, the furnace 120, the outdoor unit 144, the control unit 150, the comfort sensor 160, the display 170, may be described in the following discussion as having a local controller 290. The local controller 290 may be configured to provide a physical interface to the data bus 180 and to provide various functionality related to network communication. The SC 230 may be regarded as a special case of the local controller 290, in which the SC 230 has additional functionality enabling it to control operation of the various networked components, to manage aspects of communication among the networked components, or to arbitrate conflicting requests for network services among these components. While the local controller 290 is illustrated as a stand-alone networked entity in FIG. 2, it is typically physically associated with one of the networked components illustrated in FIG. 1.

FIG. 3 illustrates a high-level block diagram of the local controller 290. The local controller 290 includes a physical layer interface (PLI) 310, a non-volatile memory (NVM) 320, a RAM 330, a communication module 340 and a functional block 350 that may be specific to the demand unit 155, e.g., with which the local controller 290 is associated. The PLI 310 provides an interface between a data network, e.g., the data bus 180, and the remaining components of the local controller 290. The communication module 340 is configured to broadcast and receive messages over the data network via the PLI 310. The functional block 350 may include one or more of various components, including without limitation a microprocessor, a state machine, volatile and nonvolatile memory, a power transistor, a monochrome or color display, a touch panel, a button, a keypad and a backup battery. The local controller 290 may be associated with a demand unit 155, and may provide control thereof via the functional block 350, e.g. The NVM 320 provides local persistent storage of certain data, such as various configuration parameters, as described further below. The RAM 330 may provide local storage of values that do not need to be retained when the local controller 290 is disconnected from power, such as results from calculations performed by control algorithms. Use of the RAM 330 advantageously reduces use of the NVM cells that may degrade with write cycles.

In some embodiments, the data bus 180 is implemented over a 4-wire cable, in which the individual conductors are assigned as follows:

R—the “hot”—a voltage source, 24 VAC, e.g.

C—the “common”—a return to the voltage source.

i+—RSBus High connection.

i−—RSBus Low connection.

The disclosure recognizes that various innovative system management solutions are needed to implement a flexible, distributed-architecture HVAC system, such as the system 100. More specifically, cooperative operation of devices in the system 100, such as the air handler 110, outdoor unit 144, or UI 240 is improved by various embodiments presented herein. More specifically still, embodiments are presented of obtaining diagnostic information from components of the HVAC system 100, and of generating and managing alarms when exceptions to normal operation are detected.

FIG. 4 illustrates a device 410 according to the disclosure. The following description pertains to the HVAC data processing and communication network 200 that is made up of a number of system devices 410 operating cooperatively to provide HVAC functions. Herein after the system device 410 is referred to more briefly as the device 410 without any loss of generality. The term “device” applies to any component of the system 100 that is configured to communicate with other components of the system 100 over a wired or wireless network. Thus, the device 410 may be, e.g., the air handler 110 in combination with its AHC 210, or the furnace 120 in combination with its IFC 220. This discussion may refer to a generic device 410 or to a device 410 with a specific recited function as appropriate. An appropriate signaling protocol may be used to govern communication of one device with another device. While the function of various devices 410 in the network 200 may differ, each device 410 shares a common architecture for interfacing with other devices, e.g. the local controller 290 appropriately configured for the HVAC component 420 with which the local controller 290 is associated. The microprocessor or state machine in the functional block 350 may operate to perform any task for which the device 410 is responsible, including, without limitation, sending and responding to messages via the data bus 180, controlling a motor or actuator, or performing calculations. A system status display 430 is described below.

In various embodiments, signaling between devices 410 relies on messages. Messages are data strings that convey information from one device 410 to another device 410. The purpose of various substrings or bits in the messages may vary depending on the context of the message. Generally, specifics regarding message protocols are beyond the scope of the present description. However, aspects of messages and messaging are described when needed to provide context for the various embodiments described herein.

Diagnostics

Often during operation of the system 100, information regarding the operation of the system 100 may be needed by a device 410 for continued proper operation. In a bus-oriented system such as the system 100, unconstrained inquiries conveyed via the data bus 180 may disrupt normal operation and/or consume bus bandwidth needlessly. Embodiments of methods and systems of managing information requests in the system are presented herein. Such methods and systems advantageously provide efficient and timely management of information requests by the various devices 410 to provide the operator with needed information.

As mentioned above, diagnostics can be performed in one or more ways that may depend on the information contained in a particular device's status message. In some cases, diagnostics may be performed based on a class of diagnostic messages. Examples of classes, described further below, include a user interface/gateway class, a broadcast class or a dedicated diagnostic message class.

In various embodiments, a diagnostic inquiry message is sent by a diagnostic device, which could be a dedicated hardware diagnostic tool, the UI 240 or the UI/G 250. The UI 240 may be, e.g., a part of a wall-mounted device superficially resembling a conventional thermostat that provides information to and accepts input from a user. The UI/G 250 may also provide an interface from the RSBus 180 to an external network, such as the internet. The role of the UI 240 and the UI/G 250 may overlap in some respects. Herein, various embodiments are sometimes described in the context of the UI/G 250 reflecting this overlap.

Each device 410 on the data bus 180 may be configured to respond to the inquiry message. The system 100 may be configured such that some diagnostic messages do not disrupt normal device operation of the various devices 410 therein. For example, the diagnostic messages may have a priority lower than a priority assigned to messages related to normal operation of the system 100. In some embodiments, however, a privileged class of diagnostic messages may be defined, for which the system 100 is configured to provide a greater priority than routine message traffic.

In various embodiments, devices 410 are configured to recognize and respond to a privileged message that is a member of a privileged class of messages. For convenience herein, the privileged class is referred to without limitation as Class 6 diagnostic messages. The device 410 may be configured to respond to a Class 6 message in any operating state of the device 410. In some embodiments, the device 410 is configured to respond to the Class 6 message as soon as possible after power-up. For example, a startup state machine sequence may enable the device 410 to respond to a Class 6 message before the state machine enables any other functionality of the device 410.

Each device 410 may be configured to send and receive Class 6 messages. Class 6 messages include bits that may be used to address a particular device. These bits are referred to herein as Device Designator (DD) bits. Devices 410 that are disabled or have not been fully configured may still send and receive Class 6 messages. In some cases a message may also include an Equipment Type (ET) designator to identify a specific logical device when more than one logical device is embodied by a single physical device.

A device 410 may have a dedicated diagnostic mode, referred to herein without limitation as Level 1 Diagnostic Mode. The device 410 may enter the Level 1 Diagnostic Mode upon receipt of a message from another device 410, e.g. the UI 240 or UI/G 250. The device 410 may exit the Level 1 Diagnostic Mode upon receipt of an exit message from another device 410, e.g. UI 240 or UI/G 250, or upon timeout. The receiving device 410 may remain in the Level 1 Diagnostic Mode indefinitely, or for a limited time, depending on the message sent.

During the Level 1 Diagnostic Mode the device 410 may receive a Class 6 diagnostic message. The diagnostic message may be sent by the aSC 230 a. In one embodiment the diagnostic message includes a parameter value to be saved in a memory location associated with that parameter. In another embodiment the message includes a request that the device 410 publish a message containing the value of a parameter of interest. The request may be for a single Class 6 message including the parameter of interest, or for a series of Class 6 messages sent periodically including a current value of the parameter of interest. A Class 6 message may be spontaneously sent by the device 410 when a parameter value changes.

The system 100 may be configured such that the device 410 must operate in the Level 1 diagnostic mode when the device 410 is in a predetermined state. For example, without limitation, such a predetermined state may be an Installer Test state reserved for use by a system installer or service provider. In some embodiments each device 410 associated with the data bus 180 is configured to support the Level 1 diagnostic mode. A device 410 supporting Level 1 diagnostics may enter this mode upon receipt of a suitable directive from the UI 240, e.g. a message sent over the data bus 180. Such a message may include one or more dedicated bits, the state of which conveys information to the device 410. In one embodiment, the message may include an Enter bit that when set instructs the device to enter the diagnostic mode. In another embodiment, a bit signals a device 410 to remain in a diagnostic mode indefinitely when set, but to automatically exit the diagnostic mode after a predetermined period when the bit is reset.

The device 410 may be further configured to exit the Level 1 diagnostic mode upon receipt of another suitable directive via a message from the UI 240. The message may again include a dedicated signal bit, such as the Enter bit. In this case, the Enter bit may, when reset, instruct the device 410 to exit the diagnostic mode. Alternatively, the device 410 may automatically exit the Level 1 diagnostic mode after the expiration of the predetermined period described above.

In some embodiments, devices 410 may be configured to send a periodic diagnostic message at regular intervals, e.g., once per minute, or in the event of a parameter change. A parameter is a datum associated with an operational aspect of the system 100, such as a fan speed setting. Level 1 diagnostic messages may include such periodic diagnostic messages. Periodic messages may be used together with messages sent in the course of normal operation, e.g., device status messages, that continue to be sent at regular intervals during Level 1 diagnostics. In some embodiments device 410 may be configured to receive a message from the data bus 180 while in Level 1 diagnostic mode and in response thereto store a parameter value included in the message.

In various embodiments, the system 100 is configured to include various diagnostic capabilities. Each device 410 associated with the data bus 180 may be configured to periodically broadcast a Class 6 diagnostic status message, reflecting its operational status. Each device 410 may have a unique status message defined for that device 410. Due to system bandwidth limitations and message latency issues, it may be disadvantageous for the device 410 to provide all of its diagnostic information on the bus at all times. For instance, the network 200 may be unable to accommodate the amount of diagnostic data that would result if each device 410 coupled to the network 180 were to continuously provide all its diagnostic data simultaneously with the other devices 410. In such a case, limits on bandwidth of the data bus 180 would likely result in delays in reporting Class 3 Device_status messages that would temporally decouple presentation of the status to the operator, e.g. on the display 170, from the real-time state of the reporting device 410. The probability of a decoupling delay will generally increase as the number of devices 410 and the amount of data to be reported increase.

To preserve the real-time nature of the data reported to the operator, in an advantageous embodiment such a diagnostic mode is enabled only for a limited time, and on a proper subset of the devices 410. A proper subset is a subset of the devices 410 that lacks at least one of the devices 410. In some embodiments the proper subset is a single device 410. In some embodiments, the subset is enabled automatically in a certain operating state, such as an installer test state. In some embodiments, the subset is enabled by an explicit command via a message from the aSC 230 a.

Once placed in the level 1 diagnostic mode, the device 410 may periodically send a Class 6 diagnostic status message upon the expiration of a first predetermined time interval, determined, e.g. by an internal timer, without further intervention by the aSC 230 a. In some embodiments, the device 410 may automatically send a class 6 diagnostic status message when an internal parameter value changes. In some embodiments, the device 410 sends a class 6 diagnostic status message in response to a single query by the aSC 230 a, referred to herein as a query-response type message. In some embodiments, the message priority of a class 6 diagnostic status message sent automatically by the device 410 is higher than that of a query-response type message, so that the query-response type message, if executed, does not interfere with the real-time nature of the automatically sent class 6 diagnostic status messages. In various embodiments the device 410 exits the diagnostic mode upon receipt of a terminating message from the aSC 230 a, or upon the expiration of a second predetermined timer interval determined, e.g., by the internal timer.

In some embodiments, the system 100 and associated devices 410 are configured to provide for setting and retrieving operational variables in the devices 410. These variables may represent an internal state of equipment, operating statistics, etc. For example, the UI 240 may issue a specific message to which the device 410 is configured to respond with operational data. A successful read may be indicated by a suitable response message, while an unsuccessful read may be indicated by an error message. Device variables may also be written to a device 410 via a suitable message. The device 410 may respond to such a message with a suitable acknowledgment with appropriate acknowledge bits set.

The diagnostic read and write inquiries may be governed according to suitable rules, such as the following, presented by way of example without limitation:

Diagnostic read inquiries may be requested at any time, without limitation by operational mode of the subject device 410.

Diagnostic write inquiries may be executed only while the device 410 is in an idle mode, e.g., when there is no other demand on and no service provided by the device 410.

One or more bits of a query number associated with the inquiry may be reserved to signal that a diagnostic write inquiry associated with the query number may only be executed by the device 410 while the device 410 is disabled.

One or more bits of the query number may be reserved to signal that a diagnostic write inquiry associated with it may be executed by the device 410 at any time.

Illustrative Embodiments

In an embodiment, a UI 240 is configured to display diagnostic information related to a device 410 on the data bus 180. In conventional HVAC systems, to the extent that diagnostic information regarding a system component is displayed, the information is displayed at the component. For example, diagnostic information regarding a conventional furnace must typically be viewed at the furnace in a conventional system.

In contrast to conventional HVAC systems, embodiments within the scope of the disclosure provide the ability to view diagnostic information via the UI 240 or the UI/G 250, either of which may be physically located remote from the device 410 associated with the displayed information. In this context, “located remote from” means the UI 240 or UI/G 250 is not located in a same enclosure, or similarly physically associated. However, the UI 240 and the device 410 may be located near one another or even mounted on a common surface, such as a wall, and remain “located remote from” each other. Thus, e.g., where the device 410 includes the furnace 120, the information may be viewed at a location of the UI 240, e.g. a wall-mounted enclosure or a service diagnostic tool. In some embodiments, the UI/G 250 is configured to make the diagnostic information available over the internet. For example, the UI/G may be configured to send an email message to one or more preselected addresses, or may connect to a server or diagnostic terminal at the site of an installer or manufacturer. Thus, a user, service provider or OEM may be apprised of diagnostic information related to the operation of the system 100 at a remote location using any conventional means to retrieve information over the internet. In an embodiment, the system 100 is configured to send an alert via email to a property owner or operator to convey an alert thereto.

In another embodiment, the UI/G 250 includes a gateway, such as an internet port, that allows a dealer to remotely log in to the system 100 to perform diagnostics. In the broadest sense, any diagnostics and tests that can be performed from the UI 240, which may in some cases be embodied in a wall-mounted enclosure, could be performed remotely by the dealer or manufacturer (hereinafter referred to as a “remote operator”). In some cases the remote operator may then determine the source of a problem with the system 100 more quickly than making a house call. In cases where the problem can be solved by a configuration change or alarm reset, e.g., the remote operator may then resolve the problem remotely. For example, the remote operator may remotely instruct the UI/G 250 to issue a message over the data bus 180 to change a parameter value, e.g., to change a fan speed setting. If a problem cannot be solved remotely, such as a failed motor, the remote operator can determine what replacement/repair parts and/or tools will be required to correct the problem, and place any orders necessary for replacement parts. Advantageously, the remote operator is thus able to operate with greater efficiency and provide a higher level of service to the homeowner than is possible with a conventional HVAC system.

FIG. 5 illustrates an embodiment of a HVAC data processing and communication network generally designated 500. The network 500 includes two subnets 510, 520 configured to communicate therebetween over a serial bus 530. The subnet 510 has an aSC 540 and devices 550 associated therewith. Similarly, the subnet 520 has an aSC 560 and devices 570 associated therewith. The subnet 520 is also illustrated having an optional iSC 580 associated therewith. The aSCs 540, 560 are active subnet controllers, while the iSC 580 is an inactive subnet controller. Each subnet 510, 520 may operate autonomously of the other, or in some cases one of the aSC 540 or the aSC 560 may assert control over the subnet 510, 520 associated with the other of the aSC 540 or the aSC 560. Thus, for example, the aSC 560 may control devices located in the subnet 510. Such cross-subnet control may be advantageous, e.g., when whole-house control is desired of an otherwise zoned HVAC system.

FIG. 6 illustrates a method generally designated 600 of remotely servicing an HVAC data processing and communication network. A method of manufacturing may include configuring the relevant elements of the system 100 to operate as described by the method 600. Without limitation, the method 600 is described in the context of field testing and verifying the status of an air duct in the system 100 in which the indoor unit 148 is equipped with a variable speed blower. The method 600 may be used, e.g., to determine a flow limitation of the air path of the system 100. The method 600 begins with a state 605 which may be entered from any appropriate operating state of the system 100. The method 600 may be implemented using the aSC 230 a, or a controller located with the indoor unit 148. In some embodiments, the method 600 is implemented by the AHC 210.

HVAC systems may suffer from a limit on airflow through the air duct system due to high static pressure at a given operating condition. The indoor blower may be unable to maintain a set rate of air delivery, a situation sometimes referred to by those skilled in the pertinent art as a “cutback” mode. Operation in this mode may increase operating costs of the system 100 and/or risk unsafe operating conditions. An operator often is unable to test operation of an HVAC system in the cutback mode, or to determine the marginality of the system airflow setting. This inability is especially acute in a zoned system employing dampers 115 (FIG. 1) that may additionally increase the static pressure in the ducts (not shown).

In a step 610, the indoor unit 148 operates a blower to output air at a first power level or revolutions per minute (RPM). The indoor unit 148 may receive a suitable instruction from a controller, e.g., the aSC 230 a or a stand-alone diagnostic tool coupled to the data bus 180 via a diagnostic port, via a message delivered over the data bus 180. The first air flow may be, e.g., 50% of a rated maximum air flow. In a step 620, the flow rate resulting from the first power level is determined. Such determination may be made by way of a flow meter installed at an outlet of the blower, e.g., or down stream in an air duct. The flow meter may be, e.g., a hot-wire or propeller type, and may be configured to communicate over the data bus 180 to receive command messages and provide flow data. The first power level may be reported to the aSC 230 a via a message, or may be retained locally for future computation by a controller located at the indoor unit 148. In a step 630, the indoor unit 148 operates at a second power level greater than the first power level. The second power level may be greater than the first power level by an increment, e.g., about 5% of a maximum power level of the blower. Without limitation, an increment of about 5% advantageously provides a sufficiently small quantum of flow resulting from the power level increase without resulting in an unduly long test procedure. In a step 640, the flow rate resulting from the increased power level is determined.

In a decisional step 650 a difference between the second determined flow rate, from the step 640, and the first determined flow rate, from the step 620, is determined. If the determined difference of flow rate is about proportional to the difference of power level corresponding to the difference of flow rate, then the method 600 branches to the step 630 to again increase the power level of the blower. By proportional, it is meant that the increase of air flow rate resulting from the increase of power level is about the same proportion of the flow rate before the increase as is the increase of power over the power before the increase. In other words, when the increase of flow rate is about proportional to the increase of power, a 5% increase of power will result in about a 5% increase of air flow. The loop including the steps 630, 640, 650 may be timed to limit the increase of power to the blower to a specified value, e.g., 5% per minute.

If in the step 650 the increase of air flow is determined to be not proportional to the increase of power, then the method 600 advances to a step 660. This transition represents the onset of cutback mode in the flow of air from the air handler 110. The air handler 110 reports the power level associated with the onset of the cutback mode and/or an air flow value, e.g., via a message. This information may be reported locally or to a remote manufacturer or dealer site for appropriate action. The method 600 ends with a state 695, from which operation of a calling routine may resume operation.

FIG. 25 illustrates a configuration of the system 100 for determining a fault condition of the system 100 when a demand unit 155 fails to provide its primary service as expected. In some cases, a failure of the system 100 to perform as expected is detectable by comparing the temperature of discharge air 2510 of the demand unit 155, as measured by a discharge temperature sensor 2520, to an expected trend. For example, if a service demand by the aSC 230 a calls for heat from the indoor unit 148 or the furnace 120, then the discharge temperature may be expected to increase relative to an ambient temperature. On the other hand, the discharge temperature may be expected to decrease relative to the ambient temperature. If the discharge temperature fails to follow the expected trend in either of these cases, a system fault may be generated.

FIG. 26 illustrates a method generally designated 2600 of operating the network 200 to determine and report a failure of the discharge air of a demand unit 155 to follow an expected temperature profile. A method of manufacturing the network 200 may include configuring various components of the system 100 to implement the method 2600. The method 2600 begins with a state 2605, which may be entered from any suitable operating state of the system 100. In a step 2610, the aSC 230 a sends a message to the demand unit 155 requesting a service, e.g., outputting heated air. In a step 2620, the aSC 230 a monitors messages published by the sensor 2520 reporting a measured temperature of the discharge air 2510, and monitors messages published by the comfort sensor 260 reporting an ambient temperature. In a decisional step 2630, the aSC 230 a compares the discharge air temperature to the ambient temperature. In the event that discharge temperature is consistent with the active service demand, e.g. heating, then the method 2600 advances to a state 2695, from which the system 100 may resume operation from a calling routine, e.g. In the event that the discharge temperature is inconsistent with the active service demand, the method 2600 branches from the step 2630 to a step 2640. Determining whether the discharge temperature is consistent with the active service demand may include, e.g., determining a profile of temperature vs. time and comparing the temperature-time profile to an expected profile or family of profiles; determining a temperature change, resulting from the service demand, of the discharge air 2510 relative to the ambient; taking into account a delay time associated with the discharge temperature; or and providing a temperature range around the ambient temperature, outside of which the discharge temperature is considered to be consistent with the active service demand.

The step 2640 may be an optional step in which one or more mitigating steps may be taken, including waiting an additional time for the discharge temperature to change, reasserting the service demand, or checking for any alarm conditions related to the operation of the demand unit 155. The method 2600 advances from the step 2640 to a step 2650, or directly from the step 2630 to the step 2650 if the optional step 2640 is omitted. In the step 2650, the aSC 230 a determines that the demand unit 155 is malfunctioning and issues one or more alarms. The alarms may be generated to notify the user, the installer, or both (as described further below) of the failure. The method 2600 the ends with the terminal state 2695.

Alarms

As set forth in detail below, various devices in the HVAC data processing and communication network may be configured to provide an alarm under certain predetermined conditions. Various embodiments make use of a hierarchy of alarm states. Broadly, three levels of alarms are defined in one embodiment: minor alarms, moderate and critical alarms. These priorities may be encoded in bits of an alarm message to signal a device receiving the alarm of the alarm level.

In an embodiment, minor alarms are generated in response to a momentary event that has no significant bearing on the overall operation of the system 100. These events are usually transient in nature and typically are resolved without intervention by the operator. In various embodiments, alarms have a User Notification flag, Notify_User, and a Dealer Notification flag, Notify_Dealer, which may be set to indicate that a user (e.g., homeowner) or dealer should be contacted regarding the alarm. The User Notification Flags provide the ability to customize alerts that a remote entity receives and those that a homeowner receives. In some embodiments, all minor alarms have a their Notify_User and Notify_Dealer flags set to FALSE, meaning a user or dealer need not be altered to the alarm condition.

Moderate alarms may indicate a problem of a potentially more serious nature than problems that generate a minor alarm. These alarms may serve as indicators of possible product performance deterioration, or as advanced warnings of an impending malfunction. Devices may be configured to require intervention by the operator to clear the moderate alarm from memory. In some embodiments, all moderate alarms have their Notify_User and Notify_Dealer flags set to FALSE.

In various embodiments critical alarms are reserved for critical situations. Critical situations are non-recoverable problems that normally require service by a technician to repair. These alarms can also serve as general critical warnings. User or technician intervention is typically needed to clear these alarms from system memory. Unless stated otherwise, critical alarms have their Notify_User and Notify_Dealer flags set to TRUE.

In other embodiments, the setting of the User Notification Flags depends on alarm attributes other than the alarm level. In one embodiment, the Notify_Dealer flag is set for alarm messages of all levels originated by a new model of a system device 410, allowing a dealer to track alarms in a more detailed manner than alarms from more established devices 410.

Any of the minor, moderate and critical alarms may be a continuous alarm or an event alarm. Continuous alarms may be persistent, meaning the alarm condition may be removed only by correcting the root cause of the alarm, e.g. a hardware failure. These alarms generally are associated with a sensor associated with a failing device. For example, a blower may have a sensor that reports a failure of communication with an associated motor. In another aspect, a continuous alarm may be associated with a failure that prevents the device 410 from performing a basic service for which it is intended.

Event alarms may be triggered by an event that is in progress. These alarms can be cleared by a device that is the source of the alarm upon a request message from the UI 240 or the UI/G 250. For example, upon request from the UI/G 250 or the aSC 230 a, a device 410 may retry an operation, the previous failure of which resulted in an alarm state. If the device 410 is successful in performing the requested operation, then the event alarm is cleared. The number of consecutive event alarm events may be tracked, and an action taken in response to the number of events. An event-type alarm may have an associated specific timeout condition specified. This may be a simple time period (e.g., an alarm condition may time out after the time has passed and the service bits are restored), certain condition criteria (e.g., such as clearing of another alarm), or any combination of both. When an alarm is posted on the data bus 180, it may remain active until an alarm clearing message is sent out by the device 410 associated with that specific alarm. That device 410 sends out the alarm clearing message on the data bus 180 to notify other devices 410 in the system 100 of the alarm being cleared. The device may also update a status message thereof whose contents may be displayed by the UI 240 to reflect the highest level of currently active alarms, if there are any. The alarms may be noted by the aSC 230 a and locally stored in the RAM 330 or the NVM 320 of the device 410 and on one or more subnet controllers 230 in the network 200. For example, minor alarms may be stored in the RAM 330, while moderate and critical alarms may be stored in NVM 320.

Alarms may be cleared by a method that depends on the class of the alarm. Minor alarms may be cleared when the device 410 is reset. Reset may be in response to power-up or a reset instruction received from the aSC 230 a, e.g. In some embodiments, consistent with the potentially more serious nature of moderate and critical alarms, such alarms are only cleared by a more deliberate action. In one embodiment, moderate and critical alarms are cleared only in one of three ways. In a first clearing procedure, a moderate or critical alarm is cleared by some physical action required by a device 410 associated with the alarm. A physical action may include, e.g., pressing a button or momentarily connecting electrical terminals provided for this purpose. In another procedure, the device 410 detects that the condition triggering the alarm no longer exists and clears the alarm independent of intervention external to the device 410. In a third procedure, the alarm may be cleared by a clearing message generated by the UI 240 upon request by the operator. A minor alarm may also be cleared by any of the procedures used to clear a moderate or critical alarm. In some embodiments, minor alarms are always cleared when the device is reset. In such a case the alarm clearing messages are not sent out by devices for those affected minor alarms.

In an embodiment, the UI 240 includes a display screen and is configured to display a status of an alarm timeout condition. The display screen may be touch-sensitive, allowing a user to enter an alarm-related command by contacting the display screen. For example, a virtual slide switch may be displayed that reflects the current status of the alarm. As used herein, a virtual switch is a graphic displayed on a touch-sensitive screen that is configured to alter the graphic in response to touch to mimic the operation of a physical switch. The operator may disable the timeout condition by sliding the virtual switch to a disabled position. An alarm condition that is normally associated with a timeout may be cleared. Thus the alarm may be converted from one that clears upon the expiration of a timeout period to one that is cleared upon command by other means as described previously.

In various embodiments, the device 410 includes the system status display 430. The system status display 430 is a display local to the device 410 that may provide limited information to an installer to aid assessing system 100 function. The system status display 430 may include, e.g., one or more LEDs configured to flash in manner that conveys information to an observer. In some embodiments, the system status display 430 includes more than one color of LED, and information is conveyed to the observer using more than one color.

In some embodiments, the system status display 430 is configured to convey information regarding an alarm status of the system 100. In one embodiment, the system status display 430 flashes an LED at a characteristic rate, e.g., 2 Hz, when the device 410 detects Comfort_Sensor_Status message on the data bus 180. The comfort sensor 260 may periodically send the Comfort_Sensor_Status message indicating current ambient temperature and humidity readings detected by the comfort sensor 260. In some cases, e.g. for a comfort sensor 260 remote from the aSC 230 a, a device ID of the comfort sensor 260 may be set via a DIP switch on the comfort sensor 260. In some embodiments, it is an error condition when more than one system device 410 has the same device ID associated therewith. For example, two or more comfort sensors 260 or two or more displays 170 may inadvertently be assigned a same device ID. To assist the installer quickly identify such an error condition, in one embodiment a system status display 430 associated with a first comfort sensor 260 having a device ID is configured to flash at a characteristic rate when the first comfort sensor 260 detects a Comfort_Sensor_Status message on the data bus 180 that originates from a second comfort sensor 260 having the same device ID. In another embodiment, the system status display 430 of a device 410 is configured to provide a visual signal when the device 410 detects a message on the data bus 180 indicating a critical alarm is active.

In various embodiments, the system 100 is configured to allow a system alarm to be bypassed before a timeout period associated with that alarm has expired. In one embodiment, operation of a device 410 is inhibited while a system alarm associated with that device 410 is active. For example, the device 410 may include the furnace 120. A failure of a component of the furnace 120 may render the furnace 120 incapable of operating normally in some aspect. The local controller 290 associated with the furnace 120 may generate a disabling system alarm indicating the existence of the failure, with the active status of the alarm inhibiting further operation of the furnace 120. As used herein, a disabling system alarm is an alarm for which the device 410 issuing the alarm and/or the aSC 230 a is/are configured to disable a primary service provided by the device 410. The alarm may have a timeout associated with it, the expiration of which re-enables operation of the furnace 120.

In some cases, however, it may be desirable to operate the furnace 120 prior to the timeout of the alarm in spite of the component failure, e.g., for diagnostic purposes. The UI 240 may provide a system mode switch, e.g., in a setup utility screen, that allows the operator to enable bypassing the system alarm. The UI 240 may present a single bypass switch that allows all disabling system alarms to be bypassed, or a switch for each alarm for which bypass capability is desired.

Accordingly, FIG. 11 presents a method generally designated 1100 of operating an HVAC data processing and communication network, e.g., the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1100. The method 1100 begins with a state 1105, which may be entered from any suitable operating state of the system 100.

In a step 1110, an HVAC device, e.g. the device 410, generates a disabling system alarm. The alarm may be in response to a condition of the device 410 that precludes normal operation thereof. The alarm may have a timeout period associated therewith, the expiration of which cancels the alarm state and any effects associated with the existence of the alarm state. In a step 1120, normal operation of the device 410 is disabled. The disabling may be a result, e.g., of action by the local controller 290 associated with the device 410 that generates the alarm, or may be a result of an instruction issued by the aSC 230 a in response to the disabling system alarm that directs the device 410 to cease providing its primary service. In a step 1130, an alarm message is displayed on a screen of the UI 240. The alarm message includes a virtual switch configured to cancel the disabling system alarm. Display of the virtual switch may be enabled by a system 100 configuration setting, as described above. In some cases, the virtual switch is configured to allow disabling of the alarm before the expiration of a timeout period associated with the alarm. In a step 1140, the alarm is canceled in response to manipulation of the virtual switch. The cancellation restores operation of the device 410 that is the source of the alarm. The cancelling may be caused by, e.g., the aSC 230 a or by the local controller 290 responding to a message sent by the UI 240 in response to the screen manipulation. The method 1100 ends with a state 1195 from which operation of a calling routine may resume.

The UI 240 may display data from device status messages, e.g., on a display screen. In general, a Device_status message may indicate the operational and/or alarm state of a device 410 on the data bus 180. For convenience herein, Device_status messages are referred to without limitation as Class 3 system broadcast messages. Class 3 system broadcast messages may be broadcast from one subnet, but all devices from all subnets can listen and respond to them. System broadcast messages include without limitation alarms messages and Device_status.

Any device 410 may be configured to generate a message when an alarm is set or cleared. A message may be displayed on the UI 240 to indicate that an alarm is set or cleared for data logging and/or human debugging of the system 100. In one embodiment, a Device_status message indicates the instantaneous state of that device. If the status message indicates that the device 410 is ready to operate, such as after the device 410 times out an active event-type alarm, the aSC 230 a treats it as operational and proceeds with the appropriate demand messages, e.g., messages configured to command the device to perform an HVAC function. The device 410 receives this demand message and attempts to comply therewith. If the device 410 does not detect any conditions inconsistent with normal operation, the device 410 issues an alarm clearing message to indicate that the alarm has cleared. If the alarm condition persists, the device 410 resends a Device_status message with the bits indicating that the alarm is set. Such a Device_status message is referred to herein as an alarm message. In various embodiments the device 410 may optionally send a second Device_status message that includes bits indicating that one or more services provided by the device 410 are unavailable. In the current example of an event-type alarm, an alarm log reflects a sequence of event-type alarms as a single event comprised of a sequence of multiple consecutive events. If the alarm clears and then appears again it may be counted in the alarm log as a separate alarm.

An active alarm count may be incremented, and its multiple instances treated as one until the alarm clears. An active alarm, e.g., is an alarm that has not been cleared, and for which no alarm clearing message has been generated. Under normal working conditions, it is expected that active alarms include only event-type alarms. After the alarm is cleared, a new alarm instance may be logged.

In an example embodiment, an event-type alarm A is generated by a device 410 for a first time. The device 410 generates an active alarm log entry for A. The log may be stored in the RAM 330. Then, when consecutive instances of the same alarm A are repeated without an intervening the alarm-clearing event, an instance count in an active log is incremented accordingly. If another type of alarm, e.g., B is then generated, alarm B is added to the active alarm log as a more recent entry than A. If alarm A is then generated again, the previous log entry for alarm A entry is updated with the latest occurrence time and the occurrence count associated with alarm A is incremented. This update may be repeated any number of times as long as alarm A is not cleared. If alarm A is cleared, the previous entry for alarm A in the log is updated with a time stamp and alarm A is now considered inactive. If alarm A it is a minor alarm, it is removed from the RAM 330. If alarm A is either a moderate or a critical alarm, the log entry is copied to an event log accessible by an installer or OEM. If another instance of alarm A is subsequently generated, the subsequent alarm A is treated as a new instance of alarm A, and a new entry is generated in the active alarm log.

Continuous-type alarms may be treated analogously to the example of event-type alarms, except that an instance count need not be computed. This reflects the nature of the continuous-type alarms, e.g., they are not repeated.

Alarm Transmission

In general, a particular device 410 is configured to only send an alarm after receiving a configuration message from the aSC 230 a granting access by that device 410 to the subnet controlled by that aSC 230 a. The configuration message is designated without limitation as aSC_Device_Assignment. In various embodiments, a particular alarm message is sent at most twice. In a first instance, a device 410 sends the alarm message when the alarm condition first occurs. In an optional second instance, the device 410 sends the alarm message again when the alarm state is escalated. Herein and in the claims, escalation of an alarm means that an alarm is resent in order to alert the user, installer or OEM/dealer to the presence of the alarm. In general, it is expected that a particular alarm will be sent only once per single alarm event, and in such cases sent as soon as practicable after the occurrence of the associated alarm condition. In some embodiments, the alarm is repeated only for event-type alarms, in which the same event recurs, if the first alarm did not clear. In some embodiments, an alarm is also repeated when the alarm is escalated. In such a case all active alarm logs may increment the occurrence count for the particular alarm, but may not clear the alarm until an alarm-clearing message is received by the device 410 associated with the alarm. In some embodiments the alarm is be repeated, for a total of two alarm messages sent per alarm event, for both event-type and continuous-type alarms in order to escalate the alarm. This aspect is described further below.

In normal operation, alarms are not generally recurring. This means that if the alarm is caused by a persistent condition (e.g. an open sensor circuit), the alarm is not communicated over the data bus 180 continuously or repeatedly. In some embodiments each alarm is time stamped, with timing adjusted from the current time messages from the aSC 230 a. Furthermore, in some embodiments no particular alarm is broadcast onto the data bus 180 more often than once every 5 seconds.

In some embodiments, the alarm is sent within 1 second of the first occurrence of the alarm condition, and at most 500 ms after the alarm condition is detected by the associated device 410. Thus, in such embodiments each device 410 is configured to diagnose all alarm conditions within 500 ms of their occurrence. The alarm condition may be communicated, e.g., via the alarm message and the alarm status bits in the Device_status message. Each device 410 may be further configured to internally set the alarm bits in its Device_status message and send this message out within 100 ms of sending the alarm message. Thus, in some embodiments the two alarm messages may appear on the data bus 180 within 100 ms of each other in favorable bus traffic conditions.

Turning to FIG. 7, illustrated is a diagram of a series of states of the system 100, generally denoted 700, that represents the normal operation of the system 100 in response to an alarm condition. This example is representative of various embodiments, and presented without limitation. In the illustrated embodiment, a blower motor is associated with the AHC 210 and the IFC 220.

The state diagram 700 begins with an entry state 710 that may be entered from, e.g., a normal operating condition of the system 100. During a state 720, the AHC 210 or the IFC 220, sends a Device_status status message to the aSC 230 a indicating that the blower motor is operating. In a state 730, the AHC 210 or the IFC 220 loses communication with the blower motor. This event is the beginning of an alarm condition.

In an event 740, the AHC 210 and/or the IFC 220 broadcast on the data bus 180 an alarm signifying a failure of communication with the blower motor, in this case, e.g., Blower_Communcation_Failure. In an event 750, the AHC 210 or IFC 220 transmits a Device_status message to the aSC 230 a. The message may include an indication that a service, e.g., heating via the furnace 120, is unavailable.

In a step 760, the aSC 230 a instructs the blower to cease operation via a message configured to instruct the blower to operate at a selected level, e.g. a Blower_Demand command message. In a step 770 the UI 240 receives an alarm message from the IFC 220 or AHC 210 and displays a message via a display screen appropriate to the failure. In a step 780, the aSC 230 a transmits a command message to the UI 240, from which the UI 240 may present appropriate choices to the user for response. In the illustrated embodiment, the message is an SC_UI_Zone_Status message, e.g. The sequence 700 ends with an exit state 790, from which the system 100 may resume operation consistent with its operational status.

In an embodiment, the UI 240 includes a display, such as a touch-screen LCD. The UI 240 may be collocated with the aSC 230 a and/or the comfort sensor 260, but need not be. The UI 240 may provide a main point of contact by the operator with the system 100. When the UI 240 receives an alarm from a device 410, the UI 240 may display the alarm information in any form that is interpretable by the user.

In another embodiment, the UI 240 includes a display configured to flash a backlight when presenting an alarm message. The flashing backlight may alert the operator the presence of the alarm display, making prompt attention to the alarm condition more likely. In an embodiment, the backlight is displayed at a greater frequency for a critical alarm than for a moderate alarm. In an embodiment, the backlight is displayed at a greater frequency for a moderate alarm than for a minor alarm. In an embodiment, the backlight is displayed with greater brightness for a critical alarm than for a non-critical alarm. In an embodiment, an audible signal is emitted for one or more of the critical, moderate and minor alarms. In an embodiment, the audible signal is modulated, e.g., the pitch or intensity is temporally varied, with the modulation characteristics depending on the alarm level. For example, the audible signal may be pulsed at a greater frequency for a critical alarm than for a non-critical alarm.

FIG. 8 illustrates an embodiment of an alarm display with flashing backlight. For an unlit screen 810, the display may appear dark or may be lighted only by ambient light. For a screen 820, for which the backlight is on, the alarm display is visible to the user. The UI 240 may alternate between the unlit screen 810 and lit screen 820 until the user touches the screen. In various embodiments, the screen text may change at any time to display a new alarm message received by the UI 240.

Alarm Storage

In various embodiments, each device 410 stores alarms locally in memory, which may be located on the local controller 290. In one embodiment, the device 410 is configured to store a predetermined number, e.g. 10, of most recently cleared alarms in the NVM 320. In an embodiment, the device 410 is configured to store some or all of its active minor alarms in the RAM 330 and all of its active moderate and critical alarms in the NVM 320.

FIG. 9 illustrates a scheme of alarm storage on the local controller 290 according to one embodiment of the disclosure. An NVM block 910 pertains to device-level critical and moderate alarms. A RAM block 920 pertains to device-level minor alarms, and includes a RAM 922. The NVM block 910 includes an active alarms buffer 912 and an inactive alarms buffer 914. The maximum size of the buffer 912 need be no greater than the maximum number of unique alarms the device associated with the buffer 912 can generate simultaneously. The buffer 914 may serve as an alarm log for reference by an installer or OEM. The buffer 914 may be as deep as deemed practical to provide a historical record, e.g., 100 events.

An NVM block 930 pertains to subnet controller (SC)-level active and inactive critical and moderate alarms. The NVM block 930 may store alarms for all devices in the subnet associated with a particular SC 230. In the example illustrated, active alarms are interleaved with inactive alarms, but of course other arrangements are possible depending on the order in which the alarms are generated. A RAM block 940 pertains to SC-stored active or inactive minor alarms. The NVM block 930 and the RAM block 940 may be as deep as desired, illustrated for example as 100 entries.

In the embodiment of FIG. 9, a RAM block 950 pertains to the alarm storage by the UI 240 or the UI/G 250. The RAM block 950 may store critical, moderate and/or minor active and/or inactive alarms. The RAM block 950 may be as deep, e.g., as maximum number of active alarms expected to be generated in all the devices 410 on the data bus 180, or as small as a number of events to be stored as an installer alarm log, here illustrated as 10, e.g. For all the NVM/RAM blocks 910, 920, 930, 940, 950 the alarm events may in various embodiments be stored in order of a time stamp assigned to each alarm event. In an embodiment, the time stamp is the time stamp of the initial occurrence of the alarm.

In some cases a device 410 may generate an alarm prior to reaching a startup state, such as after power-up. In such cases, an associated alarm message may be broadcast on the data bus 180 as soon as the device 410 is correctly assigned to a subnet. In an embodiment, a moderate or a critical alarm may be copied into the NVM 320 of the associated device 410 only after the device 410 determines that the subnet of which the device 410 is a part has completed startup.

In some cases a previously existing alarm, e.g. an alarm stored in the NVM 320 before device reset, is cleared prior to receipt of a first message, designated without limitation as aSC_Current_Time, received by the associated device 410 setting a current time. In such a case, a message clearing the alarm, designated without limitation as aSC_Alarm_Clear, may be sent by the aSC 230 a as soon as practicable, or as soon as the device 410 is admitted to its subnet. The device 410 may be admitted to the subnet via receipt of an aSC_Device_Assignment message from the aSC 230 a, e.g. The alarm clearing event may be stored in the NVM 320 with the associated clearing time stamp left blank until the first aSC_Current_Time message is received by the device 410, at which time the blank time stamp may be updated with the correct time, and the NVM 320 record updated. When the device 410 comes out of reset, it may be configured to detect that the clearing time stamp of one or more alarms in the alarm log is blank. In such a case, the device 410 may updates each empty time stamp with the first value of current time received via aSC_Current_Time. In some cases an alarm may be generated and cleared before receipt of the first aSC_Current_Time message by the device 410. In such a case, the alarm may be stored in the RAM 330 and then copied into the NVM 320 when the aSC_Current_Time message is received and its time stamps are properly adjusted.

It is generally preferable to store all critical and moderate alarms in the NVM 320 of each device. In some embodiments, the device 410 may be configured to check the state of its alarms upon power-up. In some embodiments, if there are any active alarms still present in the NVM 320, their presence may be indicated in Device_status messages starting with the first status message issued by the device after reset. In other embodiments, the device 410 issues upon power-up a Device_status message without any alarms indicated, even when active alarms are present in the NVM 320. In such cases, the device 410 may be configured to send a Device_status message with alarms indicated after the device 410 verifies that the alarm condition still exists.

Clearing Alarms

In various embodiments, the device 410 is configured to “own” the alarms it generates. In some embodiments only the device 410 that generates a particular alarm may clear that alarm. The device 410 may clear the alarm, e.g., upon receipt of a clearing message, designated without limitation as UI/G_Device_Clear_Alarms, or upon determination by an internal diagnostic routine. In some embodiments, a device 410 is configured to clear an alarm upon command by a service technician, e.g., by depressing a switch. While the aSC 230 a may store all alarms, it may not have permission to clear an alarm. However, the aSC 230 a may be configured to monitor alarms and log an event when it determines the occurrence of an alarm clearing message from the device 410 confirming that an error has been cleared.

If an alarm is cleared by device reset, the device 410 may send a clearing message after reset upon entering a COMMISSIONING state immediately after the device 410 broadcasts its first Device_status message. In such a case the clearing time stamp is derived from the first properly received aSC_Current_Time message.

Retrieving Alarms

In one embodiment, each device 410 is required to keep an alarm log in its NVM 320. This alarm log may be organized into three sections: Active Alarm log, Installer Alarm log and OEM Alarm log. The Active Alarm log contains all types of alarms that are currently active. The Installer Alarm log may be smaller than the Installer Alarm log and in various embodiments contains a device-specific number, e.g. 10, of only the most recently cleared alarms. The OEM Alarm log may contain a larger number of the most recently cleared alarms, e.g., 50. Both Installer and OEM logs may be configured as FIFO buffers. In some cases, only Active Alarm and Installer Alarm logs can be cleared. The alarm logs may be used to diagnose each device and are advantageously accessible via messages broadcast via the data bus 180.

An alarm may be retrieved by, e.g., point-to-point communication of the UI 240 with a specific device 410. This process may be an alarm retrieval session initiated by a message, designated without limitation as UI/G_Device_Alarm_Session, from the UI 240 or the UI/G 250 to the device 410. The device 410 may acknowledge the message with a message, designated without limitation as Device_Alarm_Session_Ack. Advantageously, the device 410 may be configured to operate normally during the interrogation by the UI 240 or UI/G 250. In some embodiments, if a new alarm condition is detected by the device 410 during interrogation then the alarm message is broadcast immediately. In some embodiments, the alarm message is buffered and only added to the device alarms log after the currently ongoing interrogation is complete.

Alarms may be retrieved by UI 240 or the UI/G 250 one-by-one by sending an alarm request message designated without limitation as UI/G_Ask_For_Device_Alarm and receiving from the device 410 an alarm reporting message designated without limitation as Device_Alarm_Report. The alarms may be numbered by their order in each respective log, with the most recent alarm being the number one alarm.

The UI 240 or the UI/G 250 may signal the end of an alarm retrieval session with a particular device 410 under interrogation by sending a message, designated without limitation as UI/G_Device_Alarm_Session, to that device 410. The device 410 may acknowledge the UI/G_Device_Alarm_Session message with a message, designated without limitation as Device_Alarm_Session_Ack. In other cases, the device 410 may terminate the session when the device 410 fails to receive an alarm retrieval message, e.g., UI/G_Ask_For_Device_Alarm, within a predetermined period, such as about 5 seconds.

In a situation in which a technician is servicing the system 100, the technician may elect to clear some specific alarms or to reset the entire Active Alarm log or Installer Alarm log on a device 410. In an embodiment, the technician initiates broadcasting a message, designated without limitation as UI/G_Device_Clear_Alarms, over the data bus 180. In some cases, the local controller 290 may be configured to disregard the message if the device 410 is not in an alarm session.

One objective of the alarm interrogation session is to quickly retrieve alarms from the devices 410 and expeditiously close the session. If a new device alarm condition is encountered during the session, the UI 240 or the UI/G 250 may be configured to reload the alarms by means of a new alarm session with the device 410 experiencing the alarm. It may be advantageous to limit operation of the device 410 to conducting an active alarm session with only one UI 240 or UI/G 250 at a time.

Unresponsive Device Alarms

On occasion, a device 410 may be become unresponsive. In some cases, a device 410 may be missing, as when it is removed for service. In such a situation, other devices 410 that communicate with the unresponsive device 410 may respond by generating an appropriate alarm. In some embodiments, the aSC 230 a is configured to distinguish between an alarm generated to signal an unresponsive device 410 and an alarm signaling a missing device 410.

In the case of an alarm signifying an unresponsive first device 410, an alarm, designated without limitation as Unresponsive_Device2, can be sent by any second device 410 whether the second device 410 is configuring an aspect of the system 100 or verifying a configuration thereof. The Unresponsive_Device2 alarm may be generated when no valid response is received from a device 410, such as when a response is completely lacking, or when an invalid response is received. Examples of invalid responses include receipt of corrupt data, or failure of the device 410 to properly acknowledge the message transaction. A modest number of attempts, e.g. 3-5, may be made to communicate with the unresponsive device 410 before issuing the Unresponsive_Device2 alarm.

The Unresponsive_Device2 alarm may be implemented differently for different devices 410 attached to the data bus 180. In one example embodiment, a first class of devices includes all devices except the UI 240, the UI/G 250 and the SC 230. For devices 410 in this first class, the Notify_User and Notify_Dealer flags of the Unresponsive_Device2 alarm message are always reset. These devices 410 may increment the alarm count as with any event-type alarm. A particular device 410 may clear the alarm when a successful communication with the same device is reestablished twice in a row.

A second class of devices includes the UI 240, UI/G 250 and the SC 230. Each of these devices keeps in its RAM 330 an Unresponsive_Device_Error_Count for each device 410 it communicates with in Subnet Startup, Commissioning, Installer Test, Link Mode and Normal Operation states. The Unresponsive_Device_Error_Count may be an integer number from 0 to 255. This value may be incremented when a new Unresponsive_Device2 alarm is raised, and decremented whenever a successful transmission is completed. In an embodiment, when the Unresponsive_Device_Error_Count exceeds a specific number, e.g. 10, the Unresponsive_Device2 alarm is escalated and is sent out with Notify_User and Notify_Dealer flags set. If the Unresponsive_Device_Error_Count subsequently decreases below 10, these two flags may be cleared. If the Unresponsive_Device_Error_Count subsequently decreases to zero, then the alarm is cleared. The Unresponsive_Device_Error_Count may also be reset by a system reset event.

Next considering the case of a missing device 410, an alarm, designated without limitation as Missing_Device2, may be sent by the aSC 230 a when a previously configured device 410 is not seen on the subnet. The Missing_Device2 alarm may be a continuous alarm, and may further include setting of the Notify_User and Notify_Dealer flags. In some embodiments, the aSC 230 a only generates the Missing_Device2 alarm in a Verification mode upon completion of the Subnet Startup state. In some embodiments, the Missing_Device2 includes the Equipment Type of the missing device 410 thereby notifying the operator which device 410 is actually missing. In general, all XXX_Device2 alarms are sent out by one device 410 (device1) to notify the operator that another specific device 410 (device2) is malfunctioning. This is generally in contrast to other type of alarm messages that are owned directly by the device 410 that is the subject of the alarm message, and indicate a problem with the owning device only. The alarm may be cleared after the next successful communication with the Device.

The aSC 230 a may generate an alarm, designated without limitation as Incomplete_System, when one or more critical devices 410 are missing on the subnet. In one example, the Incomplete_System alarm is triggered when any one of the indoor unit 148, the UI 240 or comfort sensor 260 fails to respond. The aSC 230 a may be configured to send the Incomplete_System alarm in the Configuration mode, e.g. The alarm may be cleared on reset.

The aSC 230 a may also be configured to generate an alarm, designated without limitation as Lost_Communication_with_Device2, when the device 410 in question fails to send a Device_status message within a predetermined period, e.g., three minutes. This alarm represents the state that the device 410 was previously present in the system 100 but is no longer responding. The alarm may be continuous, with Notify_User and Notify_Dealer flags set. The alarm may be cleared after the next successful communication with the previously unresponsive device 410, e.g., receipt of a correct Device_status message from that device 410.

Alarm Escalation

In some embodiments one or more devices 410 may be configured to escalate an alarm under certain conditions.

In some embodiments, only moderate alarms are escalated. Escalation may consist of asserting the moderate alarm again. In some embodiments, the Notify_User and Notify_Dealer flags are set when the moderate alarm is escalated. In some embodiments, the priority level of the alarm is increased from moderate to critical when escalated.

When escalating a continuous-type alarm, the alarm message may be sent out twice for the same alarm type. In one embodiment, in a first instance the alarm is sent with the Notify_User and Notify_Dealer flags reset. In a second instance, after a predetermined period the alarm is sent again with the Notify_User and/or Notify_Dealer flags set. As a result, the second message causes a notification on the user screen (of the UI 240, e.g.) or through the UI/G 250, or both. The predetermined period may depend on the particular device 410 and/or the alarm condition. In some cases, the second alarm message is not considered as another instance of the alarm and is therefore not logged in the alarm log of the sending device 410. However, the system log in the aSC 230 a may record the second alarm instance when the aSC 230 a is configured to make no distinction between continuous and event-type alarms.

Similarly, in another embodiment, when an event-type alarm is escalated, in a first instance the first alarm message may have the Notify_User flag reset. In a second instance the alarm is sent again with the Notify_User flag set. The second instance may follow the first instance after a number of retries that may be, e.g., specific to a particular device 410 and/or alarm condition. The second alarm may include an alarm message that is the same or a different message as a message sent by the first alarm.

Summarizing various aspects of the preceding description, from the viewpoint of user notification there are four broad categories of alarms. The alarm types include continuous-type alarms and event-type alarms, both of which can be of escalation-type or are never escalated. In some embodiments, escalation alarms may be escalated. Any of these alarms may optionally be a hidden alarm, e.g., not displayed to a user, e.g., a homeowner. The hidden alarm may be reported to an installer, manufacturer or dealer, however. A Continuous-type escalation alarm is an alarm that is reported to the user after a device and case-specific time has elapsed from the start of the alarm condition. An event-type escalation alarm is an alarm that is reported to the user after a device- and/or case-specific number of alarm events of the same type has occurred. An immediate alarm is an alarm that is reported to the user upon the first occurrence of the alarm event. Note that alarm escalation need not impact the alarm clearing mechanism, as it is expected to be used for user/dealer notification only.

Alarm Behavior on Device Reset

Each device 410 may be independently configured to determine the alarm behavior when the device 410 is reset. The following description refers without limitation to elements of FIG. 9 for reference.

In some embodiments, a device 410 may be configured to reset without automatically sending any alarm clearing message. Devices 410 may further be configured to clear the RAM 922 upon reset, and to initially disregard any alarm entries in the NVM block 910.

Upon power-up, the behavior of the device 410 depends on whether any alarm is present at that time. If no alarm is detected after power-up, the device 410 may be configured to operate normally and periodically send Device_status messages with no alarm and with default status bits, regardless of the presence of any previous alarms stored in the NVM block 910.

In some embodiments when the device 410 detects an alarm condition for the first time since the device 410 was last reset, the device 410 sends an alarm message as previously described. After sending the alarm message the device 410 may check NVM block 910 for the presence of a previously stored alarm. In the event that the NVM block 910 includes an open instance of an alarm of the same type as the current alarm condition, the behavior of the device 410 may then depend on the alarm type. For the case of a continuous-type alarm, the device 410 may take no additional action. For the case of an event-type alarm, the device 410 may increment the alarm count and record the time stamp of the last occurrence of the alarm.

If there is no open instance for the same alarm, the device 410 may open a new alarm log with a count=1 and set a first occurrence timestamp to the current time. The device 410 may then enter an alarm state, including sending of status messages with appropriate alarm and status bits.

In the event that the device 410 detects an alarm clearing condition for any alarm present in the RAM block 9200R the NVM block 910, the device 410 may than send a message consistent with clearing the alarm, and may then close the instance in the NVM block 910.

Alarm Display

FIG. 27 illustrates an embodiment generally designated 2700 of a display of the disclosure presented on a screen 2710. As illustrated the display 2700 is configured to present current conditions associated with the system 100. The screen 2710 may be, e.g., a touch-sensitive screen of the UI 240. The display 2700 includes an alerts/alarms tab 2720, which, when selected, causes the display 2700 to present to the operator an alert/alarm screen. FIG. 28 illustrates an example embodiment 2800 of a display in which alarm information is presented in an alert/alarm field 2810. In the field 2810 an alarm name and relevant alarm parameters may be displayed.

FIG. 29 illustrates an embodiment of a display 2900 in which the screen 2710 includes a “pop-up” message 2910. As used herein, a pop-up message is a transient display of information by the UI 240 that overlays previously displayed information. A pop-up message may be superimposed over a default display format such as the display 2700, and may partially or completely obscure the default format. In some embodiments, the user is forced to respond to the pop-up message 2910, e.g. by touching the screen 2710, to return the screen 2710 to its default display. In some cases, such as for a minor alarm or a service reminder, the pop-up message 2910 may include a selection allowing the user to postpone action. For example, in a pop-up message regarding a scheduled filter change, the UI 240 may display to the user a virtual button labeled “remind me later” or “already performed service.” Selection of the former may cause the UI 240 to display the service reminder again at a later time, while selecting the latter may cancel the reminder.

FIG. 30 illustrates an embodiment in which the presence of an alarm is indicated by a linking icon 3010. The linking icon is advantageously designed to visually alert the operator to the existence of a state or event that potentially has a significant effect on the operation of the system 100. The linking icon 3010 is active in the sense that touching the linking icon 3010 on a touch-screen display causes the screen to transition to another display. In one embodiment, the screen transitions to the display 2800 to conveniently display the alarm information associated with the state or event to the operator.

In an embodiment, the linking icon 3010 is color-coded according to the level of the alarm associated with the alarm state or event. Thus, for example, a yellow linking icon 3010 may be associated with a minor alarm, an orange linking icon 3010 may be associated with a moderate alarm, and a red linking icon 3010 may be associated with a critical alarm. In an embodiment, when multiple alarm states simultaneously exist, the color of the linking icon 3010 reflects the level of the most sever alarm.

The linking icon 3010 may be displayed when an alarm status field of a Device_status message sent by one or more of the devices 410 indicates the presence of an alarm state. In some embodiments, the alarm status field is a two-bit field encoded for no alarm, minor alarm, moderate alarm and critical alarm. The aSC 230 a, upon receiving a Device_status message from a device 410 that indicates an alarm state may send a message to the UI 240 instructing the UI 240 to display the linking icon 3010. The message may include a color corresponding to the message severity, e.g., minor, moderate or critical.

The device 410 indicating an error state may also provide a service bit indicating a service associated with the error. The service may be, e.g., dehumidification, humidification, cooling, heat pump heat, electric heat, gas heat, and air movement (blower). In an embodiment, each device 410 provides service status bits via a message to the aSC 230 a. The status bits may be, e.g., set (1) when the service is available, and reset (0) if the service is unavailable. In an embodiment, each device provides a status bit corresponding to each service available in the system 100. Thus, for example, each device 410 may report a status bit indicating the availability of a heating service, whether or not that device actually is configured to provide a heating service. If the device 410 is not so configured, the device 410 may report a set status bit for that service.

The aSC 230 a may perform a logical AND of the status bits corresponding to a particular service, e.g., heating. If any of the devices 410 report a reset status bit for a particular service, the result of the logical AND will be FALSE, and the aSC 230 a will determine that the service is not available. In some embodiments, the aSC 230 a includes its own service status bits when performing the logical AND.

The aSC 230 a, in addition to communicating the alarm severity to the UI 240, may also communicate the service that is unavailable. The UI 240 may use this information when it responds to selection of the linking icon 3010 by the operator.

Thus, in an embodiment, when the operator selects the linking icon 3010, the UI 240 may present the display 2800. In some embodiments, the UI 240 presents the most severe active alarm to the operator. In the event that the operator dismisses the alarm currently displayed, the UI 240 may present to the operator information related to the next most severe alarm. The UI 240 may continue to present successively less severe alarms until all active alarms have been displayed.

In various embodiments, the aSC 230 a takes no action in response to determining that an alarm is active other than instructing the UI 240 to provide information to the operator, e.g., via the linking icon 3010. In such embodiments, the control of the system 100 by the aSC 230 a is regarded as decoupled from the alarm functions of the system 100. Any change to the control of the system 100 happens, if at all, in response to the indication that a service is unavailable, e.g., from a service bit.

Example Embodiment of NVM Alarm Buffer and Log

Due to life-cycle constraints on the NVM 320, it may be undesirable to repeatedly store alarm data in a same location in the NVM block 910, as doing so may significantly reduce the expected life of the NVM cell in which the data are stored. In the following illustrative embodiment two buffers are implemented in a manner that advantageously avoids concentrated use of a particular NVM storage location, and the resulting risk of early failure of the NVM 320.

FIG. 10A illustrates an embodiment of alarm storage implemented to advantageously distribute data among the storage locations of the NVM 320. A physical NVM block 1010 is configured to store alarm data. The NVM block 1010 holds all critical and moderate alarms, including active and inactive alarms. Storage locations in the NVM block 1010 are tagged by the time of the first occurrence of the alarm stored therein. Thus, for example, the alarm stored at location 104 occurred at time T93, while the alarm stored at location 103 occurred at time T92 which precedes T93 in time. Data stored in the NVM block 1010 may be logically separated into three logical storage blocks, an Active Critical and Moderate Alarm Buffer 1020, an Installer Log 1030 and an OEM Log 1040. The buffer 1020 and both logs 1030, 1040 use the first occurrence time stamp to order their alarms. The Installer Log 1030 includes the most recent 10 alarms from the OEM Log 1040.

The size of the NVM block 1010 is determined by the maximum number of concurrently possible Moderate and Critical alarms in the device 410, 12 in this example. The length of the OEM Log 1040 is set to 100 as a balance of cost versus storage depth. Thus the total size of the NVM block 1010 is 112 alarm storage locations. At a time T150, a Critical alarm is generated and it becomes active, stored in the block at the address 111. Since there are only 11 active alarms in the NVM block 1010, the length of the buffer 1020 is 11, and the length of the OEM log 1040 is 101.

Turning to FIG. 10B, illustrated is the state of the NVM block 1010, the buffer 1020 and the logs 1030, 1040 at a time T170. At T170 another Critical alarm is generated in the illustrated example. The NVM block 1010 is searched for the oldest entry of an inactive alarm. In the illustrated example, the alarm occurring at T12 residing in memory location 2 is oldest. The alarm occurring at T170 is thus placed in that location. The state of the buffer 1020 and the OEM log 1040 reflect the replacement of the alarm at T12 with the alarm at T170. The updated NVM block 1010 now includes 12 active alarms, and the length of the OEM log 1040 is reduced to 100.

By replacing the oldest inactive alarm, write operations to the NVM block 1010 are advantageously balanced over time over all the storage locations therein. Thus, the NVM 320 is less likely to fail due to overuse of any particular storage location, and the operating life of the device with which the NVM block 1010 is associated is extended.

In another illustrative embodiment, the system 100 is configured to allow the operator to establish predetermined selection criteria, e.g. filters, to determine the type of information the operator would like to receive, and how the operator would like to receive that information. For example, the dealer could configure the system 100 to send an alert message if a piece of equipment experiences some intermittent problem that the homeowner would most likely not notice. The system 100 may be configured to refrain from alerting the homeowner. Thus potential nuisance alerts for the homeowner can be avoided, but the dealer may receive information valuable to him or her.

Similarly, the homeowner may configure what types of alerts or alarms are sent to particular locations, and at what times the alerts or alarms are sent. For example, the homeowner could have a “No Heat” alarm sent to a cell phone and/or a dealer so that the problem can be expeditiously addressed. Similarly, a “Change Filter” alarm could be configured to only be sent via an email, since this alarm is less critical than the “No Heat” situation.

The discussion turns now to retention of information in an HVAC data processing and communication network, e.g. the system 100. In some cases, the system 100 configuration may change, intentionally or unintentionally. Examples of changes include failure of a system component, a transient or permanent memory failure, and a commanded or uncommanded change of an operating parameter related to a device 410. The system 100 advantageously provides, in some embodiments, for the storage by at least a first device 410 of historical configuration data pertaining to at least a second different device 410. The stored data from any one of the devices 410 holding a copy of the configuration data may be compared to current configuration data of any other device 410 with suspect configuration data. If a difference is detected between the historical data and the present data, one or more devices 410 may take remedial action appropriate to the difference detected. The data may include, e.g., operating parameters, error codes, alarm codes.

In an embodiment, a first device 410 is configured to persistently store data related to a configuration of a second device 410. The data may be stored in the NVM 320 of the first device 410. The first device 410 may store the data in response to a message sent by the aSC 230 a. In some embodiments, the first device 410 stores configuration data related to all other devices 410 on the data bus 180. In some embodiments, each device 410 on the data bus 180 stores configuration data related to each other device 410.

In an embodiment, the aSC 230 a is configured to compare the present configuration data of one or more of the devices 410 to the historical data for the same one or more devices 410. In another embodiment, a local controller 290 of a device 410 other than the aSC 230 a performs the comparison. The comparison may include sending appropriately configured messages from the aSC 230 a to one or more devices 410 being interrogated. The one or more interrogated devices may retrieve the requested information from the NVM 320 and return the data to the aSC 230 a via one or more appropriately configured messages.

The aSC 230 a, or a requesting local controller 290, may compare the historical data to the present data in any suitable manner, including, e.g., comparing a computed CRC or similar value, by performing a bit-wise comparison, or performing an exclusive OR of the data sets. If a difference between the data sets is determined, then the aSC 230 a may send one or more messages to one or more other devices 410 in the network 200 to inform the operator, installer, etc. In some embodiments, the aSC 230 a will initiate a routine to restore corrupt or missing values to the proper state based on the stored historical data.

The one or more messages sent by the aSC 230 a may include, e.g., a message commanding the UI 240 to display an alert message on a display thereof. In some embodiments, the one or messages includes a message commanding the UI/G 250 transmit alarm information associated with the alarm to an alert device. An alert device may be, without limitations, a cellular phone, a pager, a personal digital assistant (PDA), a television display, a personal computer, a computing platform running an email program. Appropriate interfacing hardware may be located locally, such as an image generating and coupling device for television display, or remotely, such as an internet server that routes an email message from the UI/G 250 to an email server or a mobile device messaging system (e.g., multimedia messaging service, a.k.a. MMS).

The homeowner, dealer or service provider may customize the system 100 to provide a selected subset of available alert or alarm messages. For example, the UI 240 or UI/G 250 may be configured to send a message to the dealer but not the homeowner when the condition resulting in the message would not normally be noticed by the homeowner, but would be relevant to maintenance of the system 100. In an embodiment the UI 240 is configured to report to the homeowner only moderate and critical alarms, while the UI/G 250 is configured to report all alarms to a remote entity (e.g., an installer or manufacturer). In an embodiment, the UI/G 250 is configured to send an appropriately configured alert message, e.g. email, to a server, thereby communicating a critical alarm to a recipient, e.g., the homeowner, installer or manufacturer. The email may be addressed, e.g., to a cellular telephone gateway that converts the alert message to a multimedia messaging service (MMS) message addressed to the homeowner's cellular telephone. Alternatively or in combination, the alert message may be addressed to an email account monitored by the installer.

In an embodiment, the UI 240 or the UI/G 250 is configured to accept input commands from the operator to enter preselected filter criteria for alert messages. Filter criteria may be programmed into the UI 240 via an appropriately configured input screen, e.g. a touch-screen, and to the UI/G 250 via an input screen of the UI 240 or from a remote host such as a desktop computer via the internet, e.g. Some filter criteria may instruct the UI 240 to display only critical alarms or only moderate and critical alarms, thereby reducing nuisance alarms to the user. Other filter criteria may instruct the UI/G 250 to route alarms of moderate severity to the installer but not the manufacturer, but to route alarms of critical severity to the installer and the manufacturer. Similarly, critical alarms may be directed by the UI/G 250 to a cell phone or pager, while moderate or minor alarms may be routed to email. In another embodiment, the UI/G 240 may be configured to send alerts to the installer or the manufacturer based on a characteristic of the device 410 sending the message. Such characteristics may include, e.g., the age of the device 410, the model number, the date or manufacture, or the class of the device (furnace or heat pump, e.g.).

The device 410 may also be configured to store tracking data. Tracking data may include manufacturing data such as an equipment and/or control serial number, equipment and/or control part number, time, date, or location of manufacture, vendor ID, country of origin, and date and location of installation. Some of such data may be installed by a manufacturer at a manufacturing site, while other of the data may be installed at installation site by an installer. The data may be stored, e.g., in the NVM 320.

In some embodiments, the aSC 230 a is configured to command, via one or more command messages, the device 410 to provide the tracking data, via one or more reply messages. The aSC 230 a may provide the tracking data to an interface device for distribution to interested parties, or may command another device 410 to read the reply messages and distribute the data. The data may be displayed locally by the UI 240, e.g., or transmitted via the UI/G 250 to a remote user. For example, a manufacturer may receive the tracking data and store it for future reference for repair or upgrade purposes, for performance analysis of installed systems, or for financial analysis.

In some embodiments, the tracking data are provided by the system 100 to a data collection device coupled to the system 100 for the purpose of retrieving the data. The data collection device may store the data for later downloading, may transmit the data wirelessly, e.g., via a cellular network, or over an optical or wired network such as the internet. The data collection device may be provided, e.g., by an installer and coupled to the system 100 wirelessly or via a suitable port provided, e.g., by the UI/G 250.

In various embodiments the tracking data are provided to a remote server, e.g. not collocated with the system 100. The remote server may include a service provider or manufacturer computer configured to communicate with the system 100 via the UI/G 250, to receive the tracking data, and to store the tracking data in any suitable format, without limitation a database. The database may be associated with the system 100 by any suitable datum, e.g., a street address, a Media Access Control (MAC) address, customer number or telephone number. The service provider or manufacturer may use the tracking data at a later date to provide service to the system 100, such as responding to a warranty claim, providing service updates, remotely reconfiguring parameter values, and the like.

Turning now to FIG. 12, illustrated is a method generally designated 1200 of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1200. The method 1200 begins with a state 1205, which may be entered from any suitable operating state of the system 100. In a step 1210, first and second system devices 410 are configured to communicate over a data bus, such as the data bus 180. The first and second system devices may be, e.g., the IFC 220 and the UI 240, respectively. In a step 1220 the second system device 410 is further configured to publish a message to the data bus 180 commanding the first system device 410 to enter a diagnostic mode. In a step 1230 the second device 410 is configured to respond to being placed in the diagnostic mode by publishing diagnostic data to the data bus 180. In an optional step 1240 the second device 410 is configured to cease publishing diagnostic data to the data bus 180. The second device 410 may cease publishing after timeout of a predetermined period, or after receiving a message from the first device 410 instructing it to do so. The method 1200 ends with a state 1295 from which operation of a calling routine may resume.

FIG. 13 illustrates a method, generally designated 1300, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1300. The method 1300 begins with a state 1305, which may be entered from any suitable operating state of the system 100. In a step 1310, a system device 410 is configured to receive a control message from the data bus 180 and operate according to a control setting communicated by the control message. The system device 410 may be, e.g., the IFC 220. In a step 1320, the system device 410 is configured to generate an alarm message in the event that the system device 410 enters an alarm state in response to an alarm condition. In a step 1330, the UI 240 or UI/G 250 is configured to receive the alarm message and display alarm information in response to receiving the alarm message. In step 1340, the aSC 230 a is configured to control operation of the system device 410 via the control message. The control is decoupled from the alarm message, as previously described. The method 1300 ends with a state 1395 from which operation of a calling routine may resume.

FIG. 14 illustrates a method, generally designated 1400, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1400. The method 1400 begins with a state 1405, which may be entered from any suitable operating state of the system 100. In step 1410, a first system device communicates over a data bus. In a nonlimiting example, the first system device is the aSC 230 a, the UI 240, or the UI/G 250, and the data bus is the data bus 180. In a step 1420, a second system device communicates over the data bus with the first system device. The second system device may be, e.g., the outdoor unit 144. The second device includes a local controller, which in turn includes an alarm memory, e.g., the NVM 320. In a step 1430, the local controller replaces an oldest inactive alarm record in the alarm memory with a current alarm record. The method 1400 ends with a state 1495 from which operation of a calling routine may resume.

FIG. 15 illustrates a method, generally designated 1500, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1500. The method 1500 begins with a state 1505, which may be entered from any suitable operating state of the system 100. In a step 1510, the system device 410 publishes an alarm message over the data bus 180 in response to an alarm condition. The device 410 may be, e.g., the outdoor unit 144. The alarm message includes a flag indicating a level of the alarm. The level may be, e.g., critical, moderate or minor. In a step 1520, a user interface, e.g. the UI 240, receives the alarm message and displays an alert, e.g., the linking icon 3010, depending on a state of the flag. For example, the user interface may display a critical alarm, but not a minor alarm, or may display the alert using colors coded by alarm severity. The method 1500 ends with a state 1595 from which operation of a calling routine may resume.

FIG. 16 illustrates a method, generally designated 1600, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1600. The method 1600 begins with a state 1605, which may be entered from any suitable operating state of the system 100. In a step 1610, a system device transmits a diagnostic information code over a data bus. The device may be, e.g., the outdoor unit 144. In a step 1620, a user interface, e.g. the UI 240, receives the diagnostic code over the data bus and displays information related to the code. The information is displayed in a located remote from the system device, such as a wall-mounted enclosure. The method 1600 ends with a state 1695 from which operation of a calling routine may resume.

FIG. 17 illustrates a method, generally designated 1700, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1700. The method 1700 begins with a state 1705, which may be entered from any suitable operating state of the system 100. In a state 1710, a system device publishes a message to a data bus. The message includes data describing an operational status of the device. In a step 1720 a user interface, e.g., the UI 240, filters the data according to predetermined criteria. In a step 1730, the user interface displays the filtered status data representing a selected subset of the status data. The interface is configurable to filter the data according to predetermined criteria and to display only a selected subset of the data meeting the criteria. The method 1700 ends with a state 1795 from which operation of a calling routine may resume.

FIG. 18 illustrates a method, generally designated 1800, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1800. The method 1800 begins with a state 1805, which may be entered from any suitable operating state of the system 100. In a step 1810 a system device, e.g., the device 410, publishes information regarding operation of the device to a data bus, e.g., the data bus 180. In a step 1820 a gateway transmits the information over the internet. In some embodiments, the information is transmitted to an installer or dealer site. In a step 1830, the gateway accepts from the internet a reply data directed to the device. The replay data may include, e.g., parameter data related to a configuration of the system 100. In a step 1840, the gateway publishes to the data bus a reply message that includes the reply data. In a step 1850 the system device receives the reply message from the data bus. The method 1800 ends with a state 1895 from which operation of a calling routine may resume.

FIG. 19 illustrates a method, generally designated 1900, of operating an HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 1900. The method 1900 begins with a state 1905, which may be entered from any suitable operating state of the system 100. In a step 1910, a user interface, e.g., the UI 240, publishes a message to a data bus including a desired relative humidity range. In a step 1920, a subnet controller, e.g., the aSC 230 a, determines that an ambient relative humidity is outside the desired range. In a step 1930, the subnet controller publishes a control message to the data bus including a service demand configured to direct a relative humidity modifying device to bring the ambient relative humidity within the desired range. In a step 1940, the relative humidity modifying device accepts the control message and operates consistent with the service demand. In contrast to conventional HVAC systems, it is unnecessary to operate a blower to implement humidification or dehumidification. This aspect provides various advantages, including, e.g., localized humidity control and increase efficiency relative to conventional systems. The method 1900 ends with a state 1995 from which operation of a calling routine may resume.

FIG. 20 illustrates a method, generally designated 2000, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 2000. The method 2000 begins with a state 2005, which may be entered from any suitable operating state of the system 100. In a step 2010, a first system device having a first local controller is configured to send and receive messages over a data bus. In a step 2020, a second device having a second local controller is configured to send messages to and receive messages from the first device over the data bus. In a step 2030 the first local controller is configured to persistently store data related to a configuration of the first and second devices. The method 2000 ends with a state 2095 from which operation of a calling routine may resume.

FIG. 21 illustrates a method, generally designated 2100, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 2100. The method 2100 begins with a state 2105, which may be entered from any suitable operating state of the system 100. In a step 2110, a system device is configured to communicate over a data bus, e.g., the data bus 180, and further is configured to store tracking data. In a step 2120, a subnet controller is configured to send a command message to the device via the data bus. The message is configured to instruct the device to publish the tracking data on the data bus via a reply message. In an optional step 2130, the system 100 conveys, via the UI/G 250, e.g., the tracking data to a remote entity, such as a manufacturer. The remote entity may use the tracking data for various purposes related to the operation or maintenance of the system 100, or other business purposes. For example, an installer may store the tracking data for future reference for repair or upgrade purposes, warranty administration or recall administration, performance analysis of installed systems, or for financial analysis. The method 2100 ends with a state 2195 from which operation of a calling routine may resume.

FIG. 22 illustrates a method, generally designated 2200, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 2200. The method 2200 begins with a state 2205, which may be entered from any suitable operating state of the system 100. In a step 2210 a subnet controller is configured to publish a control messages over a data bus. In a step 2220 a system device is configured to receive the messages and to provide an HVAC service in response thereto. In a step 2230 a gateway is configured to provide access by a remote user to the network, the access including operating the network to generate diagnostic data and retrieving the diagnostic data via the gateway. The method 2200 ends with a state 2295 from which operation of a calling routine may resume.

FIG. 23 illustrates a method, generally designated 2300, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 2300. The method 2300 begins with a state 2305, which may be entered from any suitable operating state of the system 100. In a step 2310 a system device is configured to cease providing a primary service thereof in response to a disabling system alarm generated in response to a condition of the device that precludes normal operation thereof. In a step 2320 a subnet controller is configured to disable operation of the network in response to the disabling system alarm, as a result of device having the alarm dropping its relevant service bits in its Device_status message. In a step 2330 a user interface is configured to display a virtual switch configured to cancel the disabling system alarm before expiration of a timeout period of the disabling system alarm. The method 2300 ends with a state 2395 from which operation of a calling routine may resume.

FIG. 24 illustrates a method, generally designated 2400, of operating a HVAC data processing and communication network, e.g. the system 100. A method of manufacturing the HVAC data processing and communication network may include configuring various components of the system 100 to implement the method 2400. The method 2400 begins with a state 2405, which may be entered from any suitable operating state of the system 100. In a step 2410, a subnet controller is configured to publish messages over a data bus. In a step 2420, a system device configured to receive the messages and operate in a manner consistent with control data provided thereby. In a step 2430 configuring a system status display associated with the system device to produce a visual signal when the system device detects an error or alarm condition related to operation of the system device. Specifically, the system device could be the comfort sensor 160, display 170, etc. The method 2400 ends with a state 2495 from which operation of a calling routine may resume.

Those skilled in the art to which this application relates will appreciate that other and further additions, deletions, substitutions and modifications may be made to the described embodiments. 

What is claimed is:
 1. A method of manufacturing an HVAC data processing and communication network, comprising: causing a blower and at least one other HVAC component to be coupled to one or more controllers via a data bus; associating said blower with a local controller via said data bus; configuring a duct to direct air flow from said blower; configuring said blower to receive a control message via said data bus from said local controller to provide an air flow to said duct at an initial volume rate; configuring said local controller to determine a power rate at which said air flow is provided; and configuring said local controller to increase said air flow volume rate in increments and determine a power rate increase necessary to provide said air flow volume rate increases until said local controller determines an increase in said air flow volume rate is not proportional to said power rate increase.
 2. The method as recited in claim 1, wherein said local controller is a subnet controller.
 3. The method as recited in claim 1, wherein said local controller is a stand-alone diagnostic tool.
 4. The method as recited in claim 1, wherein said local controller is further configured to transmit to a user interface via said data bus a message containing a volume rate associated with said onset.
 5. The method as recited in claim 1, wherein said increments are about 5% of a maximum power level of said blower.
 6. An HVAC data processing and communication network, comprising: a blower and at least one other HVAC component coupled to one or more controllers via a data bus; a duct configured to direct air flow from said blower; said blower configured to receive a control message via said data bus from an associated local controller; said local controller configured to command said blower to provide an air flow to said duct at an initial volume rate and to determine a power rate at which said air flow is provided; and said local controller further configured to increase said air flow volume rate in increments and determine a power rate increase necessary to provide said air flow rate increases until said local controller determines an increase in said air flow volume rate is not proportional to said power rate increase.
 7. The network as recited in claim 6, wherein said local controller is a subnet controller.
 8. The network as recited in claim 6, wherein said local controller is a stand-alone diagnostic tool.
 9. The network as recited in claim 6, wherein said local controller is further configured to transmit to a user interface, via said data bus, a message containing a volume rate associated with said onset.
 10. The network as recited in claim 6, wherein said increments are about 5% of a maximum power level of said blower.
 11. An HVAC data processing and communication network, comprising: a subnet controller coupled to a demand unit via a data bus, said subnet controller configured to initiate a test procedure by sending a message including a service demand to said demand unit; a first temperature sensor configured to measure a discharge temperature of discharge air provided by said demand unit in response to said service demand; and a second temperature sensor configured to measure an ambient temperature of a space conditioned by said network, wherein said subnet controller is further configured to take mitigating action in the event that a temperature-time profile of said discharge air relative to said ambient temperature is inconsistent with said service demand.
 12. The network as recited in claim 11, wherein said subnet controller initiates said test procedure upon entry of an instruction via a user interface coupled to said data bus.
 13. The network as recited in claim 11, wherein said subnet controller automatically initiates said test procedure periodically.
 14. The network as recited in claim 11, wherein in the event that said temperature-time profile is inconsistent with said service demand said subnet controller sends a message to reset said demand unit.
 15. The network as recited in claim 11, wherein said mitigating action is selected from the group consisting of: sending a message to a remote entity; issuing an alarm message; and disabling operation of said demand unit.
 16. A method of manufacturing an HVAC data processing and communication network, comprising: configuring a subnet controller to initiate a test procedure by sending a message via a data bus to a demand unit providing a service demand; configuring a first temperature sensor to measure a discharge temperature of discharge air provided by said demand unit in response to said service demand; configuring a second temperature sensor to measure an ambient temperature of a space conditioned by said network; and further configuring said subnet controller to take mitigating action in the event that a temperature-time profile of said discharge air relative to said ambient temperature is inconsistent with said service demand.
 17. The method as recited in claim 16, further comprising configuring said subnet controller to initiate said test procedure upon entry of an instruction via a user interface coupled to said data bus.
 18. The method as recited in claim 16, further comprising configuring said subnet controller to automatically initiate said test procedure periodically.
 19. The method as recited in claim 16, further configuring said subnet controller to send a message to reset said demand unit in the event that said temperature-time profile is inconsistent with said service demand.
 20. The method as recited in claim 16, wherein said mitigating action is selected from the group consisting of: sending a message to a remote entity; issuing an alarm message; and disabling operation of said demand unit. 